-
Notifications
You must be signed in to change notification settings - Fork 731
feat(stepfunctions): Supporting all regions in Execution ARNs #7860
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(stepfunctions): Supporting all regions in Execution ARNs #7860
Conversation
|
| */ | ||
| export function apiCallMessageHandler(request: ApiCallRequestMessage, context: WebviewContext) { | ||
| const logger = getLogger('stepfunctions') | ||
| const apiHandler = new StepFunctionApiHandler(globals.awsContext.getCredentialDefaultRegion(), context) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there plan to add the region tag to WFS handler as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
State machines have separate ARNs / ARN handling on the console side that needs to be adjusted first
|
/retryBuilds |
2b92a6f
into
aws:feature/stepfunctions-execution
Problem
Currently Execution Details only supports
us-east-1executionsSolution
Passing region parsed from execution ARN as a meta tag
Separating
apiCallMessageHandlerto Execution Details and Workflow Studio message handlers accordinglyfeature/xbranches will not be squash-merged at release time.